<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
    pageEncoding="ISO-8859-1"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>We're going to do JDBC here because we will take advantages from 
database engines</title>
</head>
<body>
	<a href="index.jsp">Back</a>
	<hr/>
	<p>Actually there's many persistence frameworks that can speed us. 
	But usually we lose much or our earned time by solving the exception cases.
	In the wrost case, we can face so many exceptions that our deadlines could 
	get lost. Also the learned framework skills are much useless on others 
	contexts.</p>
	<p>Instead of use extra libraries, techniques and configurations, we will 
	use something ligther and flexible which also give us a very powerful DSL
	(Domain Specific Language): SQL/JDBC.</p>
	<p>I's easier, older, solid, have much more documentation available and we
	can use some SQL expert to face and study the client database schema to us.
	 Usually we can use that expert to create various SQL snippets to immediate
	 use inside the project.</p>
	 <p>The applied languages there will be Java and SQL. The application 
	 language will not face SQL directly. Instead, it will recover the queries
	 through an resource file. ResourceBundle will do the job.</p>
	 <p>There are some persistence layer other possible options: whenever we 
	 need to consume COBOL services, we will look at this as a database. 
	 Sometimes even the access api resembles JDBC.</p>
	 <p>Webservice clients usually will figure as data access too.</p>
</body>
</html>